Copyright: ® 1993 Stellar Software.


Table of Contents
Write-to-help

Write-to-help is a tool that helps you turn Windows Write documents into Windows Help files.  Write-to-help is a simple workbench that contains code to translate Write files into help projects.  Write-to-help makes the act of creating good-looking help files inexpensive and painless.

Write-to-help is shareware, not freeware.  If you use this program for more than 30 days, you are required to register it.  The use of this program more than 30 days after it is installed on a computer is illegal.  The use of this program signifies acceptance of this agreement.

To register this program for use by one or more people, fill out the registration form available from the About Box.  It will calculate the registration fee.  You will be required to send a check or money order to:

Stellar Software

PO BOX 122

PEARLAND TX 77581

One of the benefits of registration is an upgrade of the program on floppy disk media of your choice.  Choose either  5-1/4" or 3-1/2" floppy disk media.  If you have the latest version, you will receive the next version as soon as it is tested and available for distribution.

If you are interested in purchasing the Visual BASIC source code, write the above address for details.

As a registered user, you have the right to make suggestions toward the improvement of this program or the development of similar programs.  If you send in a suggestion that has not been previously sent in, which is implemented in a future version of this program, you are entitled to a free copy of the executable that utilizes your idea.

If you choose not to register your copy of Write-to-help, your conscience will bother you forever.

Contents:

Configuration.

Getting started.

Procedures.

Features.

Limitations.

History.

Tips.

Statement of non-warranty.


Statement of non-warranty

This software program and its associated information is not warranted.  The entire risk and liability of using this software is yours (the user).  You alone are responsible for loss of effort, time, resources, or damage of any kind relating to the use or misuse of this software.


Write-to-help Configuration

Configuration Window...

To change the current configuration, you need to press the Config... button.  This will pop up the configuration window.  The configuration window gives you control over:

Help compiler pathname.  This is the program executed as the help compiler.

Compression.  You have a choice of (High, Medium, or None) for the amount of effort put into the compression of the final help file.  Medium compression files should be about 40% smaller.  High compression files should be about 50% smaller than uncompressed files.  The New file option indicates that the key phrase file should be deleted before invoking the compiler.  This makes compilation slower, but more compact.  The phrase file gives the help compiler a head start on compressing the file, so it makes compiling faster.  The more the help text changes, the less effective an existing phrase file will be.

Warning level.  The help compiler can output three different levels of warning and error messages.  If you want to know all the complaints of the help compiler, select All warnings.  If you only want the really important messages, select Only severe.  For a trade-off between the two extremes, select Most errors.

Build Options.  WRI to Help Project specifies that the translater should be invoked when the Build Help button is pressed.  Run Help Compiler specifies that the Help Compiler should be invoked when the Build Help button is pressed.  If you want to attempt control over your help project in a way that is not facilitated through Write-to-help, these options should be useful.

Configuration File...

The configuration file needs to be in the startup directory of the Write-to-help program.  This is typically the same directory that the program resides.  The configuration file is named WRI2HLP.INI.  The configuration file contains:

1.	The information on the Configuration Window.

2.	The current help project name.  This allows you to get productive faster.

3.	The location and size of the Write-to-help window.  Since you moved the window or resized it, this indicates a preference.  After a while you will rarely use the lower row of buttons, so you can make the window smaller by covering up the bottom buttons on the window.


Getting Started

Starting a new help project...

To start a new help project, you will need to begin a new Write document dedicated to the new help project.

It is easier to copy the template file "TEMPLATE.WRI" or another existing file rather than starting completely from scratch.  Use the File Manager's File | Copy menu option to create the new file.

After copying the file, you should start Write-to-help and change the project name to the name of your new help project.  You whould leave off the .WRI file name extension, when entering the new project name.

Once inside Write-to-help, you should press the Edit button to start the Write editor.

If you choose to copy the template file, you will need to replace the dummy values in the file and topic description sections with appropriate values.

The default (template) values relating to the entire help project are below:

helptitle: title for help window

copyright: (C) 1993 your company.

helpicon: wri2hlp.ico

contents: contents

If you do not want a custom copyright notice in the About box of WinHelp, omit the copyright statement.

If you do not want a custom icon for the help window, omit the helpicon statement.

If you do not have a table of contents, you can omit the contents statement.

Copy the template topics as needed for new topics, to reduce the amount of effort it takes to create your help document.


Procedures

How to:

Start Write-to-help

Specify help projects

Exit Write-to-help

Create topics

Create simple topic links

Create topic links with pictures

How to grab pictures


How to start Write-to-help

Starting with Program Manager Icon...

This is the preferred way to start Write-to-help.  You need to set up the program's startup directory to the directory that contains the program itself.  This is used to find a configuration file.  Once Write-to-help is started, it is ready to work on the last help project that you have been working on.

Starting via File | Run... menu...

If you start the program this way with no arguments, it will start up ready to work on the last help project you worked on.  If you supply an argument, it will be treated as the name of a help project.  The filename extension will be ignored.

Starting via drag and drop in File Manager...

A filename dropped onto the WRI2HLP.EXE program will be treated as a file in the help project.  The filename without the filename extension will be used as the project name.  So it is possible for you to drop a .WRI, .HPJ, or .HLP file onto WRI2HLP.EXE to start it up, ready to work on that help project.


How to specify help projects

Write-to-help uses a configuration file to remember the last project that you worked on.

You may specify a new help project by starting Write-to-help with a filename as a command line argument.  This can be done with drag and drop within the File Manager, or by using the File | Run... menu item in either the Program Manager or File Manager.

You can also change the name of the active help project by changing the content of the "Project" field on the Write-to-help window.


How to exit Write-to-help

The expected way to exit Write-to-help is to use the Close option on the control box of the window.  As you do this, Write-to-help will save its current configuration for future reference.  The next time you use Write-to-help, it will be set up just as it was when you terminated it the last time.


How to create topics

Each topic is a separate scrollable page of text in a help file or a pop-up definition.  A help project is limited to 1 Write document by Write-to-help, which in turn, is limited to 32767 topics.

To create a new topic, you need to create a template of the following format, and then fill out the necessary information.

Write-to-help topics consist of these parts:

1.	Help topic information.  This information is needed to describe the topic to the help compiler.

A.	Topic name  (topic: topic_name).  Every topic needs a unique name.  The name is like a variable name in most programming languages.  It has a few restrictions.

B.	Topic title (title: topic_title).  Every topic needs a title.  This is used by the History button on the help window.

C.	Search keyword (optional) (keyword: phrase[; phrase...]).  You may attach many keywords to a topic.  You may specify many keywords on one line, separated by semicolons (;).  Keywords are displayed in the help Search window.

D.	Browse sequence (optional) (browse: topic_group:seq_no).  This enables and uses the >> and << buttons on the help window.  These allow a user to page forward and backward through related topics.  There are some restrictions on browse sequence identifiers.

E.	Map context number (optional) (map: context_no).  You may assign unique context numbers to any topic to facilitate context-sensitive help.  Context numbers have a few restrictions.

F.	Config command (optional) (config: config_command).  You may put items in the [CONFIG] section of the help project file.  This example config command creates a push button entitled "Tips" at the top of the help window and makes it jump to the topic "tips" when it is pressed.  config: CreateButton( "tips", "Tips", "JumpId( `wri2hlp.hlp', `tips') ")

2.	A physical page break.

3.	Topic body of text.  This is the text that shows up in the help window.  You may mix fonts, font sizes, character attributes, paragraph attributes, and pictures as you wish.

4.	A physical page break.

Examples:

topic: limitations

keyword: Limitations

keyword: Limitations, Pictures

keyword: Limitations, Edit/Build/Try it out

keyword: Limitations, Update your OLE links

keyword: Limitations, Custom tab stops

keyword: Bugs; Limitations, Bugs

title: Limitations

browse: main:002

map: 42

    -or-

topic: pagebreak

title: Page Break


How to create simple topic links

Write does not support linked topics or hidden text as other, more expensive word processors can.  So, the specification of linked topics must be entirely visible in the document text.  I have attempted to make this as straightforward as possible.

How to specify a topic link...

To specify a topic link, you must apply the underline attribute to the text that you want to be visible in the help text and follow that text immediately with the name of the target topic.  It is necessary to make the topic name a different character attribute than the surrounding text, so it stands out for Write-to-help to pick up.

An example...

This help file is an example.  All linked topics are underlined and followed immediately by a topic name in 7 point text, which stands out from the surrounding 10 point text.  It was not necessary to make the topic name 7 point, it was just my preference.  To me, 7 point text is small but readable, and can be easily overlooked when reading the surrounding document text.  If the text were larger, it would catch my attention more and distract attention from the important surrounding text.

An example of the appearance of the text is here.

This is the text the user seesthis_is_the_topic_name.

Regular topic links vs. pop-up topics...

The text that you underline, will show up on the help text.  If you want a link to be a full jump to another topic, you apply a BOLD character attribute along with the UNDERLINE attribute.  For a pop-up topic, you leave out the bold attribute and only use the underline attribute.


How to create topic links with pictures

A picture can be made into a button that can be pressed to jump to other topics.  Since pictures can not posess the underline attribute, a different type of tag has to be used to differentiate between a simple picture and a link button.  The tag that is used is the paragraph line spacing attribute.  To declare a picture as a button, just set the picture to "double spacing".

To make a picture into a link button:

1.	Click on the picture to highlight it.

2.	Select Double Space from the Paragraph menu.

3.	Enter the name of the target topic as the text immediately after the picture.  This text needs to have a different character attribute than the surrounding text, just like simple topic links.

4.	Set the character attributes of the target topic name different than the surrounding text.  Such as changing its size.

See also, Pictures.


How to grab pictures

How to grab pictures from the screen...

Microsoft Windows provides a way to grab pictures from the screen without additional utilities.

1.	Get the image that you want to capture visible on the screen.  Move windows if necessary.  Normalize or maximize the window that you want to capture a picture from.  If you want to grab an icon, minimize the window to make its icon visible.

2.	Put the picture onto the clipboard.  If the picture that you want to capture is within a window, click on the window to focus on it.  Then press alt-PrintScreen.  This copies the image of the window to the clipboard.  If the picture that you want to capture is not inside a window, such as an icon, you will need to capture the entire screen by pressing PrintScreen.

3.	Start Paint Brush.

4.	Paste the picture into Paint Brush with SHIFT-Insert.  The picture may be clipped to the visible size of the exposed editing area, so you may need to make the Paint Brush window large enough to display enough of the picture to expose the part that you want.

5.	Clip the part of the picture that you want.  Use the scisors tool of Paint Brush to select the area that you want.  This is sometimes difficult to do, since you will have to move the pointer exactly onto the corner pixels to select the picture.

6.	Copy it the the clipboard by pressing CTRL-Insert.

7.	Paste the picture into Write with SHIFT-Insert.  The picture is now embedded in your document at the insertion point (cursor).


Features
Write-to-help features

WYSIWYG

Translates Write character and paragraph attributes directly into rich text format.  What you see is what you get!  Mix any fonts with varying sizes, and use BOLD and ITALICS anywhere you want.  You can also utilize the left margin, right margin and 1st line indent margin control in Write.

Pictures

You can link or embed 16-color bitmaps [image] from paintbrush into your write document.  You can even grab pictures from the screen. You can even make them hot spots to jump to other topics.  This bitmap is a button to jump to the topic of pictures...

Error message assistance

The help compiler produces error messages that are useful, but not as useful as they can be.  For example, a message will inform you that an unknown rtf command is present in your .rtf file, but it will tell you that it is at "byte offset 0x2F7D".  I don't know about you, but I have a difficult time finding a peice of text by its hex byte offset.  Write to help will expand many types of error messages to help you locate and diagnose the problem.

Browse Sequences and Context Sensitive Help

You can specify browse sequences that utilize the >> and << WinHelp buttons.  Write-to-help allows you to specify context sensitive help topics.

Embedded Commands

You may use most rtf commands and help macros directly inside the document to use facilities not readily available through Write.  The best way to include an rtf command is to put it in the paragraph that it affects without any special character attributes (bold or italics).  If the rtf is active until the next pard command, be aware that a pard command is automatically inserted at the end of each topic.  For help macros that you want executed as the .HLP file is loaded by WinHelp, you use the CONFIG directive in any topic header in the Write document (refer to How to create topics for more details).  For more information about the extensive array of rtf commands handled by the Help Compiler (version 3.1), refer to the Microsoft (R) Windows TM Software Development Kit Programmer's Reference, Volume 4: Resources, Chapter 15: Windows Help Statements and Macros.


Limitations
Write-to-help limitations

Windows ver 3.1...

Write-to-help was designed to be compatible with Windows 3.1.  If you are using an earlier (or later) version of Windows, you may experience problems.

All help text in 1 file...

Write-to-help relies on all of your help text being in a single Write document.  A future version may facilitate dividing your text into multiple documents.

Edit / Build / Try It Out...

If you are using SHARE.EXE, or other file sharing software, Write may lock your document file so that it is not accessible to Write-to-help.  If this is the case, Write-to-help will inform you with a dialog box telling you to exit Write before using the Build Help button.

If you are viewing the final help file with WinHelp, it will promptly commit suicide when it discovers that the HLP file it is using has changed.

Picture justification in Write...

Write does not support having a picture on the same line as text, so you have to use your imagination sometimes.  Pictures, oddly enough, have paragraph attributes attached to them.  You can place the picture on the left, center, or right by setting the paragraph alignment property.

Write-to-help pays attention to the content of the paragraph above and below a picture and will use them together.  It may be necessary for you to press return above and/or below a picture to effectively isolate it from the neighbor paragraphs.

Picture justification vs topic links...

Pictures can also be made into buttons that are linked to other topics.  However, write-to-help does not currently support filling text around a picture that is also being used as a button to jump to another topic.  This may be implemented in a future version.  In this help file, I was successful at creating a center-justified and topic-linked picture.  The reason why this works some time and not others is a mystery to me (so far).

Update your OLE links...

If you use OLE linked bitmaps, you need to update your OLE links when you get into Write each time.  If you do not update your links, the OLE headers in the Write document to not appear legal to the Write-to-help translator.

When linked OLE objects are in a file, you are prompted by Write as the file is loaded, to see if you want to update the links immediately or not.  Choose YES on the dialog box.  Another way around this problem is to embed your bitmaps instead of linking them.

Custom tab stops...

Custom tab stops in a Write file are not translated into equivalent help file tab stops.  This may be implemented in the future.

Subscript / Superscript...

Subscript and superscript text in a Write file are not translated into equivalent rtf text.  This may be implemented in the future.

Bugs...

WinHelp will ignore explicit paragraph information in some rare cases.  The case I ran into was when there was a bold 14pt phrase at the beginning of a topic body and a single line paragraph of plain 10pt text, each starting at the normal left margin.  The remainder of the topic was text with the appearance of an outline (items with tabbed subordinate items, nested) using the special left indents and first line indents.  The bug was that the two paragraphs that were at the beginning of the topic (which were supposed to begin at the far left of the page) displayed as left indented like the majority of the topic text.  The remaining topics in the help file exhibited the same erroneous left indent.  After adjusting the actual rtf file and recompiling it with many variations, I decided that the bug was in WinHelp.EXE.  This problem could drive you crazy.

Write may not allow you to edit a linked picture by double-clicking on it in some cases.  The OLE object information is correct.  The object is visible, but not easily editable.


Pictures

Insertion of pictures

Write allows you to link or embed pictures with OLE (object linking and embedding).  Write-to-help can use both linked and embedded pictures from Paintbrush.  They have to be in windows .BMP format.  You may not use multiple resolution bitmaps.  This capability may be added in a later version.

To embed a picture captured from the screen.

To embed a picture:

1.	Load the bitmap picture you want into Paintbrush.

2.	Copy the picture to the clipboard by selecting the entire picture and pressing CTRL-INS.

3.	Place the text cursor where you want the picture in the Write document.

4.	Paste the picture by pressing SHIFT-INS.  The picture will appear.

To link a picture:

1.	Load the bitmap picture you want into Paintbrush.

2.	Copy the picture to the clipboard by selecting the entire picture and pressing CTRL-INS.

3.	Place the text cursor where you want the picture in the Write document.

4.	Select Paste Link from the Edit menu.  The picture will appear.

Alignment of pictures (left, center, right)

In Write, pictures have paragraph attributes attached to them.  You can place the picture on the left, center, or right by setting the paragraph alignment property.

If you place the picture on the left, any text following the picture will be filled in around the right of the picture, placing the picture on the left.

If you place the picture in the center, [image] any text following the picture will be filled in around the picture, placing the picture in the center.

If you place the picture on the right, any text following the picture will be filled in around the left of the picture, placing the picture on the right.

To set the alignment property of a picture:

1.	Click on the picture to highlight it.

2.	Select either Left, Centered, or Right from the Paragraph menu.

Pictures as links to other topics

A picture can be made into a button that can be pressed to jump to other topics.

Pictures as icons for help macros

A picture can be made into a button that can execute a help macro.  The example (clock icon) starts the clock.exe program when pressed.

The only difference between jumping to another help topic and executing a macro is that the macro is in place of the target topic name.  Macros in text must be preceeded by an exclamation mark.

See also, How to create topic links with pictures.


Painless
Painless...

Write provides easy control over:

Specifying fonts

Setting font sizes

Assigning attributes

Specifying paragraph indents, and justification

Write-to-help provides:

Workbench to jump between editing with Write, Building Help, and viewing the final result

Easy linking of topics

Assignment of browse sequences

Painless approach to creating rich text format files

Assistance in deciphering help compiler error messages

Creating help files with only an ASCII editor in rich text format is tedious, time-consuming, and downright painful.


Write
Write is the word processor that is included in Microsoft Windows.  It is a pretty good basic WYSIWYG (What You See Is What You Get) word processor.

Write handles multiple fonts and font sizes, attributes on paragraphs and individual characters, and inclusion of pictures.  Version 3.1 uses scalable fonts and OLE (Object Linking and Embedding).  It handles most of the capabilities that you would need to create Windows help files.

Refer to your Windows documentation for details.


Shareware
Shareware is software intended to be distributed freely for potential customers to use on a trial or limited basis.  It is not free.  The license agreements vary from one product to another.  Some are for use for only a limited length of time.  Some are offered for an unlimited time, but money is required to obtain a version of the software with additional features.

Write-to-help is offered for a limited time to each potential buyer.


Freeware
Freeware is software that is absolutely free.  Write-to-help is not freeware.  It is shareware.


Notes
Special characters such as the 1/2 symbol are illegal in rtf files.


Build Help button
The Build Help button translates a Write document into a rich text format file and a help project file.  Then it starts the Microsoft Help Compiler on the project, which builds the desired HLP file.


Topic Names
Topic names can be up to 32 characters long.

They can contain letters, numbers, and underscore characters (_).

Other characters, such as symbols, spaces, tabs, etc. are illegal.


Browse name restrictions
Names used in browse sequences define the order of a browse sequence.

Each set of topics that you want to be sequenced pages must have a unique name.  Each topic needs to have a unique identifier (usually a zero-filled number).  A colon is used to separate the name and number.

The syntax of a browse sequence identifier is:

sequence_name:sequence_number

example:

MENUS:0001


Page Break
Page breaks are special characters inserted into the document text that explicitly forces a new page of text to begin.

Topic descriptions and topic bodies are separated by page breaks for Write-to-help to easily descriminate between the two types of information.

Page breaks also provide a solid beginning and end to the topic text on screen, inside the Write word processor.

To insert a page break, press CTRL-L.


Context Number Restrictions
Context numbers must be unique.

Context numbers may be decimal numbers or standard 'C' language hex numbers, such as 0x001F, which is the number 31 in decimal.


Visual BASIC

Microsoft Visual BASIC may be the ultimate tool for rapid prototyping and complete development of applications for Microsoft Windows.  In many cases, you can create applications in hours that would take days or weeks with the C compiler and SDK.  There is no comparison between the two sets of tools.


Write-to-help History

Ver	Notes

1.4	Added registration window to facilitate easier registration method.  Expanded help documentation.  Added standard .INI configuration file with reasonable defaults to remove the .CFG config file used in earlier versions.  Added a call to terminate the on-line help window when Write-to-help is terminated.

1.3	Added context sensitive help.  Expanded on-line help text for clairity.  Found possible bug in two state machines in the code (a 16bit signed integer should have been a 32bit signed integer in each case).

1.2	Added code to expand HC error messages into something easier to use.  Added code to extract embedded OLE PBrush bitmap files from the Write document.  Now you can use embedded bitmaps as well as linked ones.  This coding was difficult (Don't do this at home it is too dangerous).  Changed code to recognize when the compiler is really finished compiling (by detecting the absence of the help compiler window).  This was prompted by the discovery that if you are not using SHARE.EXE, that the outputed HLP file is not locked if share.exe is absent.  Now the code will work with or without share.exe.  Without this change, the program would assume that the compiler was finished as soon as it started and would report -3 help compiler errors.

1.1	Fixed bug in control-break hierarchy.  At the end of a paragraph, if the font changed and the following paragraph began with a topic jump, the following topic jump title would exhibit the prior paragraph's font characteristics.  Enhanced documentation.

1.0	After much frustration creating .rtf help files without adequate tools, Bobby Blythe created the product Write-to-help.  Joseph Pigadas assisted in original design and coding.


Tips

Make the Write window manageable

Write uses the full width of the screen (at least on my 640x480 VGA display).  This causes problems in using WinHelp to view the results while editing the original text.  One way to make the Write window manageable is to set the Right Margin of the document to a large size, such as 4.00".  This causes the width required to edit your document to decrease to roughly half the screen.  This permits you to see the final result side by side with the original text.  To set the Right Margin, use the Page Layout... selection of the Document menu.

Create your own templates

The templates included with Write-to-help might not be suitable for you or your applications.  You should build a template .WRI file that uses layout styles that are appropriate for your applications.  Copy your template for each new project, so you have a head start and don't have to agonize over style issues.  Also, it would be a good idea to make your help files consistent in general layout and appearance.

Set the Write-to-help window attributes

Write-to-help starts up in the same position on the screen as it was when you used it last.  So when you position the window in a stretegic position on the screen that is suitable for the way you choose to work, it will always be where you want it when you start it.  Also, the bottom two buttons are rarely used, so you may shrink the window vertically to cover them up.  This removes some of the clutter from your screen and gives you more room to work.  The window will start up with the same window height as when it was terminated.

Compression Level

To make the help compiler run faster, you should turn off the file compression (see Write-to-help Configuration for details) while developing a help file.  When you are ready to release it, you should use Medium or High compression to make the .HLP file smaller for easier distribution.

Examine WRI2HLP.WRI

This help file is distributed in its original form (wri2hlp.wri) for you to examine.  A few techniques to using Write-to-help may be better understood if you were to look at this file.

Capture your own pictures

A visual aid usually increases the reader's comprehension of surrounding text.  Of course, avoid excessive use of pictures because it looses its meaning and clutters the information that you are trying to convey.  You can easily capture a picture from a screen [image] and place it into your help file.


Project name

Specify the name of your project in this field.  It should be a complete path and file name except that a file extension is not necessary.

Example:

\vb\cookbook\cookbook

This specifies that a help project basically named cookbook inside a directory named cookbook under the vb directory is to be used.


Edit button

This button starts Write on the help document specified in the Project name field.


Build Help button

This button starts the translation and compilation process that builds your help file.  The name specified in the Project name field is used as the name

of the Write document to decipher and the help file to create.

The actions performed by the Build Help button are controlled by the Write-to-help configuration.


Try It Out button

This button starts a WinHelp window with your help file displayed.


Error window

When you press the Build Help button, error messages are placed in a pop-up window for your review.

There are two basic types of error messages: translation errors and compilation errors.  Translation errors are generated by Write-to-help.  Compilation errors are generated by the help compiler (HC).  The help compiler creates error messages that are usually clear, but it rarely gives you any useful information about where the error actually is.  Write-to-help provides you with additional information in many cases that will help you locate the source of errors easier.

The Error Window does not pop up until an error is encountered.


register
Product Registration

Stellar Software authors are supported by regristration fees sent in by customers.  Without your money, improvements to this software and the development of other packages would be impossible.

You may evaluate Write-to-help for thirty (30) days without paying for it.  If you choose not to pay for it, you are required to remove it from your computer and never use it again.

On the other hand, if you want to continue to use it beyond thirty (30) days after you first install it onto your computer, you are required to register it.  When you register this program, you will receive these benefits of registration:

One software upgrade.  This package is evolving to be easier to use and more powerful.  You will receive the latest version.  If you have the latest version, you will receive the next one when it is tested and ready for distribution.

An official registration number that you enter on the registration popup window.  This will display your name, your organization name, and the number of users allowed on your registration on the About box.

The ability to improve this program by sending in suggestions.  If your suggestion is implemented and you were the first to suggest it, you will receive the first version of this software that implements it.  If you want credit for your idea, your name will be in the history section of this help document with due notice of your idea and its implementation.

Notice of major improvements in this software package.

The ability to purchase the Visual BASIC source code.  Write Stellar Software for details.

How to register...

1.	On the about box, press the Register button.  This will display the Registration Form.

2.	Fill out this form and press the Print Registration Form button.

3.	Write a check or money order (US dollars only) for the amount shown on the form and mail it with the printed form to:

Stellar Software

PO BOX 122

PEARLAND TX 77581

4.	Soon (2 to 4 weeks later), you will receive a Registration Id through the mail.

5.	Go to the registration window again and fill in the Registration Id and press the Final Registration button.  You will be legally authorized to use this software with as many users as you specified, indefinitely.  However, you do not own the program and you can only distribute it to others as shareware.  Other people will be required to register the program with Stellar Software for their own use.

6.	Later you will recieve a software upgrade.  The software will be more recent than the version that you already have.  If you have the latest version, you will receive the next version as soon as it is tested and available for distribution.

Registration Fee...

The information that you enter in the registration form will determine the registration fee.  The fee is based on the number of users you want to register and whether or not you are in the state of Texas, for which there is sales taxes to collect.

Price schedule:

$15 for first user

$12 for each user from the 2nd to the 5th

$10 for each user from the 6th to the 15th

$7 for each user from the 16th to the 25th

$5 for each user after the 25th

All shipments outside the continental US will be charged an additional $10.

All shipments in the state of Texas will be charged 7.75% sales tax.